home *** CD-ROM | disk | FTP | other *** search
/ ftp.cs.arizona.edu / ftp.cs.arizona.edu.tar / ftp.cs.arizona.edu / icon / newsgrp / group94b.txt / 000034_icon-group-sender _Fri Sep 2 10:12:19 1994.msg < prev    next >
Internet Message Format  |  1995-02-09  |  1KB
  1. Received: by cheltenham.cs.arizona.edu; Fri, 2 Sep 1994 11:43:59 MST
  2. To: icon-group-l@cs.arizona.edu
  3. Date: 2 Sep 1994 10:12:19 -0700
  4. From: tanksley@coyote.csusm.edu (Billy Tanksley)
  5. Message-Id: <347mdj$hmq@coyote.csusm.edu>
  6. Organization: California State University San Marcos
  7. Sender: icon-group-request@cs.arizona.edu
  8. References: <33t025$ba5@highway.leidenuniv.nl>, <33tacj$pen@ios.com>, <1994Aug30.140940.5002@midway.uchicago.edu>
  9. Subject: Re: Icon - still alive??
  10. Errors-To: icon-group-errors@cs.arizona.edu
  11.  
  12. In article <1994Aug30.140940.5002@midway.uchicago.edu> goer@midway.uchicago.edu writes:
  13. >That's funny.  I feel quite the opposite.  I dread the kitchen sink
  14. >mentality - turning Icon into a heap of platform-specific extensions
  15. >geared for things that C and PERL already do much better.
  16.  
  17. Well, I agree with your fear of platform-specifisity, but _standard_ 
  18. extensions are needed.  Just look at Forth-- it's been around for a long 
  19. time, and is difficult entirely because of its lack of standard 
  20. features.  Every time a Forth programmer needs a feature, he/she writes 
  21. it himself, completely differently than another would have.
  22.  
  23. It's a pain-- don't saddle yourselves with those difficulties.
  24.  
  25. -Billy
  26. Paladin (for PC-Geos)
  27.